-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update to CRAN version 1.0.7 #340
Conversation
It gives an error or R ubuntu-latest
I re-run the tests but it persists. I don't think that it's related with the code. In the second run of the tests it gives a NOTE on mac OS because one example ran for more than 5 seconds. Is there any way to re-run only the R tests? It seems that the Re-run jobs button applies to all tests (both R and Python) |
@mlampros Thank you very much for your hard work!
We are seeing some LaTeX-related errors in LightGBM right now: microsoft/LightGBM#3997 (comment) too. Let's re-run tests tomorrow and see whether we need to dig deeper into the problem or it is temporary just due to some servers' problems.
Unfortunately, it is impossible in GitHub Actions to re-run a separate job.
|
Please increase the allowed time to run by overwriting |
I am out of ideas for this error case on ubuntu-latest. I tried various modifications in the 'r_tests.sh' file but none of these work. As a reference I'll add the following links that I stumbled upon during my search: |
So, you mean that my changes in the examples section of the package is the main reason for the error (actually the .Rd documentation error). But this error would have appeared also during the submission to CRAN, which is not the case. |
Yeah, it seems to be so.
I guess the difference in the environments of our CI and CRAN (software versions or incomplete installation, for example) led to such results. |
* fixes * test * test * fixes * fixes * fixes * fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the great job!
Cool that we don't need to regenerate docs with outdated roxygen2 version and docs are in consistency with ones on CRAN. I agree that rewriting them to fix warnings is time consuming and shouldn't have a high priority.
I left only 3 very minor code style suggestions which you can accept directly in your browser if you agree with them.
Co-authored-by: Nikita Titov <[email protected]>
Co-authored-by: Nikita Titov <[email protected]>
Co-authored-by: Nikita Titov <[email protected]>
This pull request is for the update of the RGF R package to CRAN version 1.0.7. As discussed in the comment of the pull request 338 I've modified the code because there were 2 NOTES for the Windows version that had to be fixed.
As for the additional issue of the new M1mac chip-tests that was discussed in the comment of the pull request 338 we have to keep an eye on the check results page of the R package.